Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1418

reference: 694-tree-1
name: 1418
tree-preservation-order: undefined
694-tpo-1
uprn
address-text
point: POINT (-1.011760 50.881732)
geometry: MULTIPOLYGON (((-1.011718 50.881728,-1.011719 50.881736,-1.011725 50.881744,-1.011735 50.881750,-1.011746 50.881754,-1.011760 50.881755,-1.011773 50.881754,-1.011785 50.881750,-1.011794 50.881744,-1.011801 50.881737,-1.011803 50.881729,-1.011801 50.881720,-1.011795 50.881713,-1.011786 50.881707,-1.011774 50.881703,-1.011761 50.881701,-1.011736 50.881706,-1.011726 50.881712,-1.011720 50.881720,-1.011718 50.881728)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL